Update Statistics Handling

Note: Only one Update Statistics call can run at any one time on the server.

If necessary, the settings for Update Settings may be modified to deviate from the default interval and to control when maintenance calls happen. You can add specific “Update” settings in the Configuration database SystemProperties table. The following script examples may be used as a guide:

INSERT INTO [dbo].[SystemProperties] ([FieldName],[FieldValue],[FieldType])

VALUES ('UpdateStatsIntervalMinutes','20', 1)
INSERT INTO [dbo].[SystemProperties] ([FieldName],[FieldValue],[FieldType])

VALUES ('UpdateStatsIntervalMinutes_davis_ecaptureconfig_Client00058','2', 1)
INSERT INTO [dbo].[SystemProperties] ([FieldName],[FieldValue],[FieldType])

VALUES ('UpdateStatsOnCompletion','TRUE', 1)
INSERT INTO [dbo].[SystemProperties] ([FieldName],[FieldValue],[FieldType])

VALUES ('UpdateStatsOnCompletion_davis_ecaptureconfig_Client00058','TRUE', 1)

When the database statistics are updated, the Queue Manager Log file contains an entry similar to:

"Statistics update completed in NNms on database XYZ"

The values are set to either False (off) or True (on) for the following “Update” settings:

UpdateStatsOnCompletion
- If the field is found and the value says 'FALSE', the completion check is turned off.
- If the field is found and the value contains ‘TRUE’ then the completion check is turned on. Therefore, the UpdateStatsOnCompletion_<databaseName> values may be set to either FALSE or TRUE for each individual database. See the following related setting for additional information.

UpdateStatsOnCompletion_<databaseName>
- If a database specific field is not found, then the UpdateStatsOnJobCompletion rules are applied.
- If a database specific field is found and the value is 'FALSE', then updating on Job Completion is turned OFF for both the Client database and all associated individual staging databases.

UpdateStatsIntervalMinutes
- If this field is not found, then the default value of 15 is used.
- If this field is found, then the interval value is used for all Clients that do not have a different specific interval entry. See the following related setting for additional information.

UpdateStatsIntervalMinutes_<databaseName>
- If a database specific field is not found, then the UpdateStatsIntervalMinutes rules are applied.
- If a database specific field is found, then the update interval is used for both the Client database and all associated individual staging databases.

The Queue Manager Log file now contains additional information about when a database is put on the list of databases to be updated, along with when the earliest the update will run. For example:

2017-04-06 13:32:48,715 [20] INFO QueueManager.QMMaintenance - Queued database DG_F_eCapFI_Client00002 for statistics update at or after 1:47 PM

The Log file now displays information about when a database is put into the Update Statistics queue. For example:

2017-04-06 13:35:09,514 [56] INFO QueueManager.QMMaintenance - Queued database DG_F_eCapFI_Client00002 for statistics update [interval]

2017-04-06 13:35:09,514 [56] INFO QueueManager.QMMaintenance - Queued database DG_F_eCapFI_Client00002 for statistics update [job completion]